[issue #54] Fixed auth compatibility with EKS serviceAccount roles #57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In EKS environments, each container on a single host can have its own credentials.
Authentication is supported via a mechanism of 'serviceAccounts' (a kubernetes term).
boto3.Session().get_credentials().method
returns assume-role-with-web-identity which is another form of iam role based credentials.Current implementation only allows
iam-role
,assume-role
but notassume-role-with-web-identity
.